Seamless data movement and metadata management in a hybrid cloud setting using a configurable micro services based architecture

ABSTRACT

A system for data migration is disclosed. The system may receive a migration request comprising a source file path and a target file location. The system may capture source file metadata based on the source file path and the migration request. The system may transfer a source file from a first data environment to an intermediate data environment via a first transfer process. The system may transfer the source file from the intermediate data environment to a second data environment via a second transfer process.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/583,846, filed on Sep. 26, 2019, the complete disclosure of which isincorporated herein by reference.

FIELD

The present disclosure generally relates to systems and methods formigrating data between data environments.

BACKGROUND

Traditional methods of data management typically rely on multipleon-site and off-site data environments and cloud environments. Atechnical problem exists in that differing data environments tend tocomprise a variety of formats, interfaces, securities, and transferprotocols. Therefore, data movements between environments may encounterconflicting protocols and may be further complicated by ad-hoc userrequirements. Furthermore, errors may be introduced in data transfersbetween environments which may not be reported or captured. In thisregard, electronic data migration and analysis by traditional methodsmay be time consuming, may demand a relatively large number of userinputs, and may be intolerant of informational faults.

SUMMARY

In various embodiments, systems, methods, and articles of manufacture(collectively, the “system”) for data migration are disclosed. Thesystem may receive a migration request comprising a source file path anda target file location. The system may capture source file metadatabased on the source file path and the migration request. The system maytransfer a source file from a first data environment to an intermediatedata environment via a first transfer process. The system may transferthe source file from the intermediate data environment to a second dataenvironment via a second transfer process.

In various embodiments, the system may generate a parquet file set basedon the target file location. The system may generate a native agentinstruction set based on the source file metadata. The system mayconduct a schedule of operations based on the native agent instructionset via a native agent of the first data environment. In variousembodiments, the system may search the parquet file set for a sensitivedata element and generating a message in response to the sensitive dataelement. The system may receive an approval message and exiting a holdstate. The system may update a status dashboard with at least one of aprocess status and a module status.

The foregoing features and elements may be combined in variouscombinations without exclusivity, unless expressly indicated hereinotherwise. These features and elements as well as the operation of thedisclosed embodiments will become more apparent in light of thefollowing description and accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter of the present disclosure is particularly pointed outand distinctly claimed in the concluding portion of the specification. Amore complete understanding of the present disclosure, however, may beobtained by referring to the detailed description and claims whenconsidered in connection with the drawing figures, wherein like numeralsdenote like elements.

FIG. 1 is a block diagram illustrating various system components of asystem for data migration, in accordance with various embodiments;

FIG. 2 illustrates a process for error monitoring and reporting in asystem for data migration, in accordance with various embodiments;

FIG. 3A illustrates a process for data migration between a first dataenvironment and a second data environment in a system for datamigration, in accordance with various embodiments;

FIG. 3B illustrates a continuation of a process for data migrationbetween a first data environment and a second data environment in asystem for data migration, in accordance with various embodiments; and

FIG. 3C illustrates a continuation of a process for data migrationbetween a first data environment and a second data environment in asystem for data migration, in accordance with various embodiments.

DETAILED DESCRIPTION

The systems and methods provide a greater level of sophistication andcontrol for migration of data between data environments. Benefits of thepresent disclosure may apply to, for example, any sort of dataenvironment. In that regard, the present disclosure may apply instructured data environments, unstructured data environments, datalakes, cloud storage environments and/or the like.

The current system provides a technical solution by enabling a commonstructure for data migration across a plurality of environments. Thesystem may provide a variety of user access levels (e.g., permissions)associated with the plurality of environments. The system may increasethe speed and efficiency of data processing and data migration. Thesystem may reduce the process time a data migration process is engagedby a user or system. The system may also reduce redundant migrationrequests by decreasing migration errors, and thereby reducing a demandfor system resources. The system may simplify data sorting, routing, andprocessing and enhance user experience by decreasing a number of userinteractions. In various embodiments, the system may tend to enableenhanced data security and integrity by migrating data between a firstdata environment and a second data environment via an intermediate dataenvironment. In this regard direct connections between the first and thesecond environment may be inhibited and leakage of sensitive data may bereduced.

The process also improves the functioning of the computer. For example,the process increases the reliability and speed of data migration byreducing the number of user inputs, by bypassing a number of user inputrequests and/or by enabling discrete reporting of migration processerrors. Similarly, the process increases the reliability and speed ofdata presentation by enabling automated data migration and reporting. Invarious embodiments, the processes described herein may increase networkavailability by reducing front end and back end process calls and/ornetwork hops and duplicate migration operations. The processes may alsosave processing resources including CPU time, memory resources, andnetwork resources. In various embodiments, the system may convert sourcefiles into a compressed parquet format tending thereby to save networkbandwidth during data transfer operations. The system may perform asensitive element check on the compressed (parquet) file tending therebyto reduce data processing time. In like regard, the system may tend toincrease available storage space by conducting operations on the parquetfiles thereby reducing data overhead. In various embodiments, the systemmay parallelize a number of jobs to service multiple requests tendingthereby to maximize available bandwidth and increase data processingspeeds.

In various embodiments, and with reference to FIG. 1, a system 100 fordata movement and metadata management may comprise a first dataenvironment 102, a second data environment 104, an external dataenvironment 106, and a migration service 108. Any of these componentsmay be outsourced and/or be in communication with system 100 andmigration service 108 via a network. System 100 may be computer based,and may comprise a processor, a tangible non-transitorycomputer-readable memory, and/or a network interface, along with othersuitable system software and hardware components. Instructions stored onthe tangible non-transitory memory may allow system 100 to performvarious functions, as described herein. In various embodiments,migration service 108 may be configured as a central network element orhub to access various systems, engines, and components of system 100.Migration service 108 may comprise a network, computer-based system,and/or software components configured to provide an access point tovarious systems, engines, and components of system 100. Migrationservice 108 may be in operative and/or electronic communication with auser 110 via a user device. The migration service 108 may include amigration API service 112, a workflow scheduler 114, a data mover module116, and a metadata database 118. In this regard, the migration service108 may allow communication between the user 110 via the user device andthe systems, engines, and components of system 100.

In various embodiments, a user device may comprise software and/orhardware in communication with the first data environment 102, thesecond data environment 104, and/or the migration service 108 via anetwork comprising hardware and/or software configured to allow a user,and/or the like, access to the migration service 108 and source data 122(i.e., source file). The user device may comprise any suitable devicethat is configured to allow a user to communicate with a network and themigration service 108 via a command line interface 124. The user devicemay include, for example, a personal computer, personal digitalassistant, cellular phone, kiosk, and/or the like and may allow a userto transmit command lines to the system 100.

In various embodiments, and as described in further detail herein, thefirst data environment 102 may comprise a data lake, e.g. largestructures of data stored without regard to a common format. The seconddata environment 104 may comprise a cloud resource. Each of the dataenvironments (102, 104) may be internal to a private network (i.e., aninternal data environment), whereas the external data environment 106may be widely accessible on a public network. The workflow scheduler 114may be configured to generate and task native agents 120 of the dataenvironments (102, 104). For example, the workflow scheduler may includea polling module configured to communicate with the metadata database118, a Directed Acyclic Graph (DAG) generator module 135, and a DAGexecutor module 138. In like regard, the data environments (102, 104)may include native data processing modules 126 configured to communicatewith the migration service 108 via the migration API service 112

In various embodiments, internal and external data environments (102,104, 106) and the metadata database 118 may include any number of datastructures or data elements. Metadata database 118 may be configured tomaintain case type data such as, for example, migration service 108status and source data 122 metadata such as, for example, number ofcolumns transferred, size of files, file paths, data type, datastructure, user information, and/or the like. In various embodiments,the native agents 120 may include modules particular to the dataenvironment such as, for example, a pre work module 140, a sensitivedata element check module 142, and a data movement module 144. Invarious embodiments and in like regard, the data mover box 116 maycomprise one or more modules such as second data mover module and/or ahive metastore module. The second data mover module may be configured tocommunicate with the external data environment. The hive metastoremodule may be configured to communicate with a hive database of theexternal data environment.

With reference to FIG. 2 in various embodiments, a process 200 (e.g., insystem 100) for error reporting is illustrated. The system may receive amigration request from user 110 via command line interface 124 (step202). The migration request may include a source file 122 path and atarget endpoint for the source file 122. In various embodiments, thesource file and the endpoint may be in any of the data environments(102, 104, 106). In this regard, the system 100 may migrate data betweenin internal data environment (102, 104) to an external data environment106 or vice versa. In response to the migration request, the system maystart a native data processing module 126 of the source file 122 dataenvironment such as, for example, the first data environment 102 (step204). The native data processing module 126 includes a parquet convertermodule 128, a validation module 130, and a metadata capture module 132.Step 204 includes capturing a source file metadata 134 by the metadatacapture module 132. In various embodiments, the source file metadata 134may include, for example, number of columns transferred, size of files,file paths, data type, data structure, user information, start and endtimestamps of the transfer, component status, transfer status, predictedtransfer time and/or the like. The system may store the source filemetadata 134 in the metadata database 118. Step 204 includes updating astatus dashboard with a process status and a module status based on theprocess step and active module. For example, the process status may be“prework” and the module status may be “metadata capture”.

The native data processing module 126 may apply a parquet conversionfunction to the source file 122 to generate a parquet file 137 (step206). In response to generating the parquet file, the native dataprocessing module 126 may submit a migration job to the workflowscheduler 114 via the migration API service 112 (step 208). Themigration job may include the source file metadata 134 and the parquetfile 137. Step 208 includes updating the status dashboard with a processstatus and a module status. For example, the process status may be“submitted” and the module status may be “parquet completed”. Step 208includes storing the source file metadata to the metadata database 118.In various embodiments, the workflow scheduler 114 includes a DAGgenerator 136 and a DAG executor 138. In response to receiving themigration job, the DAG generator 136 of workflow scheduler 114 maygenerate a native agent instruction set based on the source filemetadata 134. The workflow scheduler 114 may generate the native agentinstruction set based on a pre-defined template which may compriseconfigurable steps to suit various modules in the native environment. Invarious embodiments, the native agent instruction set includes aschedule of operations conducted by a native agent to affect a migrationof the source file to the target endpoint (e.g., external dataenvironment 106). The DAG generator may pass the native agentinstruction set to a DAG executor 13 which, in response, may start oneor more modules of the native agent 120 based on the schedule ofoperations in the instruction set.

In various embodiments, the DAG executor 138 may start a pre-work module140 of the native agent 120 (step 210). Step 210 includes updating thestatus dashboard with a process status and a module status. For example,the process status may be “in progress” and the module status may be“prework in process”. The pre-work module 140 may format the source datafor a database 107 of the target environment to generate a target theand to update the module status to “prework completed” (step 212). Invarious embodiments, the pre-work module 140 may create intermediatestaging directories where the native agents may write intermediate dataand/or logs. The pre-work module 140 may update the module status. Thepre-work module 140 may change or alter permissions on intermediate datato system ID and, in this regard, may enable user specific accesscontrols and/or restrictions to the data. In various embodiments, thepre-work module 140 may have contextual security permissions and mayhave limited super user privileges to operate within the director of aparquet file and, thereby, the pre-work module may make changes to thefile permissions. In this regard, the various systems and modules incommunication with the pre-work module 140 may continue further dataoperations in a secure manner.

The DAG executor 138 may start a sensitive data element check module 142of the native agent 120 (step 214). The sensitive data element checkmodule 142 may search the target the for Personally IdentifiableInformation (PII) such as, for example, card member numbers, socialsecurity numbers, etc. (i.e. a sensitive data element). The sensitive,data element check module 142 may generate an alert in response to thePII in the target file and update the module status to “PII checkcompleted” (step 216). In various embodiments, if PII is detected withina file, an alert may be generated and the transfer process may be put onhold and the system may set the module status to “PII check failed”. Theprocess may haft in response to detecting the PII and await an approvedtransfer command. In response to receiving the approved transfercommand, the system may proceed with the migration process (i.e. proceedto step 218). The DAG executor 138 may start a data movement module 144of the native agent 120 (step 218).

The data movement module 144 may package and pass the target file to adata mover module 116 of the migration service 108. Step 218 may includeupdating the module status to “DM box move in progress”. In response toreceiving the target file, the native, agent of data mover module 116 ofthe migration service 108 may pass the target file to the database 107of the external data environment 106 (step 220). Step 220 includesupdating the module status to “DM box move completed”. The system mayupdate the module statues once the data mover module 116 completes thetransfer. The system may determine a success or a failure of target filemigration to the external data environment 106 (step 222). In responseto determining a failure, the system may update the process status to“transfer failed” and the module status to “public cloud movementfailed” (step 224). In response to determining a success, the system mayupdate process status to “transfer completed” and the module status to“public cloud movement successful” (step 226).

In various embodiments and with additional reference to FIGS. 3A through3C, a process 300 (e.g., in system 100) for data migration between afirst data environment and a second data environment is illustrated.User 110 may submit a login request comprising user credentials to aninternal data environment of system 100 such as the first dataenvironment 102 and/or the second data environment 104 (step 302). Thesystem may determine access to the migration service 108 based on theuser credentials (step 304). In response to an invalid user credential,the system may deny access to system 100 and generate an access request(step 306). In response to a valid user credential, the system mayreceive a migration request including a source file location and atarget file location via the command line interface 124 (step 308). Thesystem may check the migration request for errors such as, for example,a syntax error (step 310). In response to determining an error, thesystem may prompt the user to reenter the migration request (step 312).In response to the migration request, the system may start a parquetfile conversion process (step 314). The parquet file conversion processmay generate a parquet file set based on the target file location (step316)

In various embodiments, the system may check for errors in the parquetfile conversion process and/or the parquet file set (step 318). Inresponse to an error in at least one of the parquet file conversionprocess or the parquet file set, the system may start an error reportingprocess (step 320). The error reporting process may generate an email tothe user comprising an error description related to the error in atleast one of the parquet the conversion process or the parquet the set.In various embodiments, any of the modules and components of the systeminvoked by a native agent may be configured to report successes anderror codes which may be configured to trigger a module status update.The workflow scheduler may monitor the module status reporting duringthe transfer process and may be configured to proceed to the next modulewhere modules report successes or terminate jobs where the currentmodule reports failures. The system may start a prework process inresponse to generating the parquet file set (step 322). The system maygenerate a post-work file set based on the parquet file set (step 324).The system may search the post-work the set for PII (step 326). Inresponse to finding PII within the post-work file set, the system maygenerate a PII hold email comprising an approval link and enter a holdstate (step 3203. The system may prompt the user 110 with a status holdmessage (step 330). In various embodiments, the system may receive a PIIdeny message and, in response, may start the error reporting process(step 320). The error reporting process may generate a message such as,for example, an email to the user comprising an error descriptionrelated to the PII deny message.

In various embodiments, the system may receive a PII approved message(i.e., an approval message), and in response, exit the hold state (step332). The system may start a first transfer process and pass thepost-work file from the internal data environment to an intermediatedata environment (step 334). Step 334 may include, for example,instructing the native agent 120 of the first data environment 102 topass a the to the migration service 108. In various embodiments, thesystem may perform an error checking of the post-work file (step 336).The system may start a second transfer process and pass the post-workfile from the intermediate data environment to an external dataenvironment defined by the target file location (step 338). Step 338 mayinclude, for example, passing the file from the migration service to theexternal data environment 106 or the second data environment 104. Invarious embodiments, the system may determine an error status of thesecond transfer process (step 340). In response to determining an errorof the second transfer process, the system may start the error reportingprocess step 320. The system may generate an email based on the errorstatus and the migration request (step 342). For example, an email maybe sent to a system user account originating the transfer request and/orto a support team. The email may comprise a unique request ID, a username, a process start time and a process end time, a log path, a datastaging path location, a module ID for any failed module, and/or anyother such data. In this regard, the system may tend to enable debuggingof failures in an accelerated manner.

The detailed description of various embodiments herein makes referenceto the accompanying drawings and pictures, which show variousembodiments by way of illustration. While these various embodiments aredescribed in sufficient detail to enable those skilled in the art topractice the disclosure, it should be understood that other embodimentsmay be realized and that logical and mechanical changes may be madewithout departing from the spirit and scope of the disclosure. Thus, thedetailed description herein is presented for purposes of illustrationonly and not of limitation. For example, the steps recited in any of themethod or process descriptions may be executed in any order and are notlimited to the order presented. Moreover, any of the functions or stepsmay be outsourced to or performed by one or more third parties.Modifications, additions, or omissions may be made to the systems,apparatuses, and methods described herein without departing from thescope of the disclosure. For example, the components of the systems andapparatuses may be integrated or separated. Moreover, the operations ofthe systems and apparatuses disclosed herein may be performed by more,fewer, or other components and the methods described may include more,fewer, or other steps. Additionally, steps may be performed in anysuitable order. As used in this document, “each” refers to each memberof a set or each member of a subset of a set. Furthermore, any referenceto singular includes plural embodiments, and any reference to more thanone component may include a singular embodiment. Although specificadvantages have been enumerated herein various embodiments may includesome, none, or all of the enumerated advantages.

Systems, methods, and computer program products are provided. In thedetailed description herein, references to “various embodiments,” “oneembodiment,” “an embodiment,” “an example embodiment,” etc., indicatethat the embodiment described may include a particular feature,structure, or characteristic, but every embodiment may not necessarilyinclude the particular feature, structure, or characteristic. Moreover,such phrases are not necessarily referring to the same embodiment.Further, when a particular feature, structure, or characteristic isdescribed in connection with an embodiment, it is submitted that it iswithin the knowledge of one skilled in the art to affect such feature,structure, or characteristic in connection with other embodimentswhether or not explicitly described. After reading the description, itwill be apparent to one skilled in the relevant art(s) how to implementthe disclosure in alternative embodiments.

As used herein, “satisfy,” “meet,” “match,” “associated with”, orsimilar phrases may include an identical match, a partial match, meetingcertain criteria, matching a subset of data, a correlation, satisfyingcertain criteria, a correspondence, an association, an algorithmicrelationship, and/or the like. Similarly, as used herein, “authenticate”or similar terms may include an exact authentication, a partialauthentication, authenticating a subset of data, a correspondence,satisfying certain criteria, an association, an algorithmicrelationship, and/or the like.

Terms and phrases similar to “associate” and/or “associating” mayinclude tagging, flagging, correlating, using a look-up table or anyother method or system for indicating or creating a relationship betweenelements, such as, for example, (i) a transaction account and (ii) anitem (e.g., offer, reward, discount) and/or digital channel. Moreover,the associating may occur at any point, in response to any suitableaction, event, or period of time. The associating may occur atpre-determined intervals, periodic, randomly, once, more than once, orin response to a suitable request or action. Any of the information maybe distributed and/or accessed via a software enabled link, wherein thelink may be sent via an email, text, post, social network input, and/orany other method known in the art.

The term non-transitory is to be understood to remove only propagatingtransitory signals per se from the claim scope and does not relinquishrights to all standard computer-readable media that are not onlypropagating transitory signals per se. Stated another way, the meaningof the term “non-transitory computer-readable medium” and“non-transitory computer-readable storage medium” should be construed toexclude only those types of transitory computer-readable media whichwere found in In re Nuijten to fall outside the scope of patentablesubject matter under 35 U.S.C. § 101.

Benefits, other advantages, and solutions to problems have beendescribed herein with regard to specific embodiments. However, thebenefits, advantages, solutions to problems, and any elements that maycause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as critical, required, or essentialfeatures or elements of the disclosure. The scope of the disclosure isaccordingly limited by nothing other than the appended claims, in whichreference to an element in the singular is not intended to mean “one andonly one” unless explicitly so stated, but rather “one or more.”Moreover, where a phrase similar to ‘at least one of A, B, and C’ or ‘atleast one of A, B, or C’ is used in the claims or specification, it isintended that the phrase be interpreted to mean that A alone may bepresent in an embodiment, B alone may be present in an embodiment, Calone may be present in an embodiment, or that any combination of theelements A, B and C may be present in a single embodiment; for example,A and B, A and C, B and C, or A and B and C. Although the disclosureincludes a method, it is contemplated that it may be embodied ascomputer program instructions on a tangible computer-readable carrier,such as a magnetic or optical memory or a magnetic or optical disk. Allstructural, chemical, and functional equivalents to the elements of theabove-described various embodiments that are known to those of ordinaryskill in the art are expressly incorporated herein by reference and areintended to be encompassed by the present claims. Moreover, it is notnecessary for a device or method to address each and every problemsought to be solved by the present disclosure, for it to be encompassedby the present claims. Furthermore, no element, component, or methodstep in the present disclosure is intended to be dedicated to the publicregardless of whether the element, component, or method step isexplicitly recited in the claims. No claim element is intended to invoke35 U.S.C. § 112(f) unless the element is expressly recited using thephrase “means for” or “step for”. As used herein, the terms “comprises,”“comprising,” or any other variation thereof, are intended to cover anon-exclusive inclusion, such that a process, method, article, orapparatus that comprises a list of elements does not include only thoseelements but may include other elements not expressly listed or inherentto such process, method, article, or apparatus.

Computer programs (also referred to as computer control logic) arestored in main memory and/or secondary memory. Computer programs mayalso be received via communications interface, Such computer programs,when executed, enable the computer system to perform the features asdiscussed herein. In particular, the computer programs, when executed,enable the processor to perform the features of various embodiments.Accordingly, such computer programs represent controllers of thecomputer system.

These computer program instructions may be loaded onto a general purposecomputer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructionsthat execute on the computer or other programmable data processingapparatus create means for implementing the functions specified in theflowchart block or blocks. These computer program instructions may alsobe stored in a computer-readable memory that can direct a computer orother programmable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the function specified in the flowchart block or blocks.The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

In various embodiments, software may be stored in a computer programproduct and loaded into a computer system using removable storage drive,hard disk drive, or communications interface. The control logic(software), when executed by the processor, causes the processor toperform the functions of various embodiments as described herein. Invarious embodiments, hardware components may take the form ofapplication specific integrated circuits (ASICs). Implementation of thehardware state machine so as to perform the functions described hereinwill be apparent to persons skilled in the relevant art(s).

As will be appreciated by one of ordinary skill in the art, the systemmay be embodied as a customization of an existing system, an add-onproduct, a processing apparatus executing upgraded software, astand-alone system, a distributed system, a method, a data processingsystem, a device for data processing, and/or a computer program product.Accordingly, any portion of the system or a module may take the form ofa processing apparatus executing code, an internet based embodiment, anentirely hardware embodiment, or an embodiment combining aspects of theinternet, software, and hardware. Furthermore, the system may take theform of a computer program product on a computer-readable storage mediumhaving computer-readable program code means embodied in the storagemedium. Any suitable computer-readable storage medium may be utilized,including hard disks, CD-ROM, BLU-RAY DISC®, optical storage devices,magnetic storage devices, and/or the like.

The system and method may be described herein in terms of functionalblock components, screen shots, optional selections, and variousprocessing steps. It should be appreciated that such functional blocksmay be realized by any number of hardware and/or software componentsconfigured to perform the specified functions. For example, the systemmay employ various integrated circuit components, e.g., memory elements,processing elements, logic elements, look-up tables, and the like, whichmay carry out a variety of functions under the control of one or moremicroprocessors or other control devices. Similarly, the softwareelements of the system may be implemented with any programming orscripting language such as C, C++, C#, JAVA®, JAVASCRIPT®, JAVASCRIPT®Object Notation (JSON), VBScript, Macromedia COLD FUSION, COBOL,MICROSOFT® company's Active Server Pages, assembly, PERL®, PHP, awk,PYTHON®, Visual Basic, SQL Stored Procedures, PL/SQL, any UNIX® shellscript, and extensible markup language (XML) with the various algorithmsbeing implemented with any combination of data structures, objects,processes, routines or other programming elements. Further, it should benoted that the system may employ any number of conventional techniquesfor data transmission, signaling, data processing, network control, andthe like. Still further, the system could be used to detect or preventsecurity issues with a client-side scripting language, such asJAVASCRIPT®, VBScript, or the like.

The system and method are described herein with reference to screenshots, block diagrams and flowchart illustrations of methods, apparatus,and computer program products according to various embodiments. It willbe understood that each functional block of the block diagrams and theflowchart illustrations, and combinations of functional blocks in theblock diagrams and flowchart illustrations, respectively, can beimplemented by computer program instructions.

Accordingly, functional blocks of the block diagrams and flowchartillustrations support combinations of means for performing the specifiedfunctions, combinations of steps for performing the specified functions,and program instruction means for performing the specified functions. Itwill also be understood that each functional block of the block diagramsand flowchart illustrations, and combinations of functional blocks inthe block diagrams and flowchart illustrations, can be implemented byeither special purpose hardware-based computer systems which perform thespecified functions or steps, or suitable combinations of specialpurpose hardware and computer instructions. Further, illustrations ofthe process flows and the descriptions thereof may make reference touser WINDOWS® applications, webpages, websites, web forms, prompts, etc.Practitioners will appreciate that the illustrated steps describedherein may comprise in any number of configurations including the use ofWINDOWS® applications, webpages, web forms, popup WINDOWS® applicationsprompts, and the like. It should be further appreciated that themultiple steps as illustrated and described may be combined into singlewebpages and/or WINDOWS® applications but have been expanded for thesake of simplicity. In other cases, steps illustrated and described assingle process steps may be separated into multiple webpages and/orWINDOWS® applications but have been combined for simplicity.

In various embodiments, the software elements of the system may also beimplemented using a JAVASCRIPT® run-time environment configured toexecute JAVASCRIPT® code outside of a web browser. For example, thesoftware elements of the system may also be implemented using NODE.JS®components. NODE.JS® programs may implement several modules to handlevarious core functionalities. For example, a package management module,such as NPM®, may be implemented as an open source library to aid inorganizing the installation and management of third-party NODE.JS®programs. NODE.JS® programs may also implement a process manager, suchas, for example, Parallel Multithreaded Machine (“PM2”); a resource andperformance monitoring tool, such as, for example, Node ApplicationMetrics (“appmetrics”); a library module for building user interfaces,and/or any other suitable and/or desired module.

Middleware may include any hardware and/or software suitably configuredto facilitate communications and/or process transactions betweendisparate computing systems. Middleware components are commerciallyavailable and known in the art. Middleware may be implemented throughcommercially available hardware and/or software, through custom hardwareand/or software components, or through a combination thereof. Middlewaremay reside in a variety of configurations and may exist as a standalonesystem or may be a software component residing on the internet server.Middleware may be configured to process transactions between the variouscomponents of an application server and any number of internal orexternal systems for any of the purposes disclosed herein. WEBSPHERE®MQ™ (formerly MQSeries) by IBM®, Inc. (Armonk, N.Y.) is an example of acommercially available middleware product. An Enterprise Service Bus(“ESB”) application is another example of middleware.

The computers discussed herein may provide a suitable website or otherinternet-based graphical user interface which is accessible by users. Inone embodiment, MICROSOFT® company's Internet Information Services(IIS), Transaction Server (MTS) service, and an SQL SERVER® database,are used in conjunction with MICROSOFT® operating systems, WINDOWS NT®web server software, SQL SERVER® database, and MICROSOFT® CommerceServer. Additionally, components such as ACCESS® software, SQL SERVER®database, ORACLE® software, SYBASE® software, INFORMIX® software, MYSQL®software, INTERBASE® software, etc., may be used to provide an ActiveData Object (ADO) compliant database management system. In oneembodiment, the APACHE® web server is used in conjunction with aLINUX®operating system, a MYSQL® database, and PERL®, PHP, Ruby, and/orPYTHON® programming languages.

For the sake of brevity, conventional data networking, applicationdevelopment, and other functional aspects of the systems (and componentsof the individual operating components of the systems) may not bedescribed in detail herein. Furthermore, the connecting lines shown inthe various figures contained herein are intended to represent exemplaryfunctional relationships and/or physical couplings between the variouselements. It should be noted that many alternative or additionalfunctional relationships or physical connections may be present in apractical system.

In various embodiments, the methods described herein are implementedusing the various particular machines described herein. The methodsdescribed herein may be implemented using the below particular machines,and those hereinafter developed, in any suitable combination, as wouldbe appreciated immediately by one skilled in the art. Further, as isunambiguous from this disclosure, the methods described herein mayresult in various transformations of certain articles.

The various system components discussed herein may include one or moreof the following: a host server or other computing systems including aprocessor for processing digital data; a memory coupled to the processorfor storing digital data; an input digitizer coupled to the processorfor inputting digital data; an application program stored in the memoryand accessible by the processor for directing processing of digital databy the processor; a display device coupled to the processor and memoryfor displaying information derived from digital data processed by theprocessor; and a plurality of databases. Various databases used hereinmay include: client data; merchant data: financial institution data;and/or like data useful in the operation of the system. As those skilledin the art will appreciate, user computer may include an operatingsystem (e.g., WINDOWS®, UNIX®, LINUX®, SOLARIS®, MACOS®, etc.) as wellas various conventional support software and drivers typicallyassociated with computers.

The present system or any part(s) or function(s) thereof may beimplemented using hardware, software, or a combination thereof and maybe implemented in one or more computer systems or other processingsystems. However, the manipulations performed by embodiments were oftenreferred to in terms, such as matching or selecting, which are commonlyassociated with mental operations performed by a human operator. No suchcapability of a human operator is necessary, or desirable in most cases,in any of the operations described herein. Rather, the operations may bemachine operations or any of the operations may be conducted or enhancedby artificial intelligence (AI) or machine learning. Artificialintelligence may refer generally to the study of agents (e.g., machines,computer-based systems, etc.) that perceive the world around them, formplans, and make decisions to achieve their goals. Foundations of AIinclude mathematics, logic, philosophy, probability, linguistics,neuroscience, and decision theory. Many fields fall under the umbrellaof AI, such as computer vision, robotics, machine learning, and naturallanguage processing. Useful machines for performing the variousembodiments include general purpose digital computers or similardevices.

In various embodiments, the embodiments are directed toward one or morecomputer systems capable of carrying out the functionalities describedherein. The computer system includes one or more processors. Theprocessor is connected to a communication infrastructure (e.g., acommunications bus, cross-over bar, network, etc.). Various softwareembodiments are described in terms of this exemplary computer system.After reading this description, it will become apparent to a personskilled in the relevant art(s) how to implement various embodimentsusing other computer systems and/or architectures. The computer systemcan include a display interface that forwards graphics, text, and otherdata from the communication infrastructure (or from a frame buffer notshown) for display on a display unit.

The computer system also includes a main memory, such as random accessmemory (RAM), and may also include a secondary memory. The secondarymemory may include, for example, a hard disk drive, a solid-state drive,and/or a removable storage drive. The removable storage drive reads fromand/or writes to a removable storage unit in a well-known manner. Aswill be appreciated, the removable storage unit includes a computerusable storage medium having stored therein computer software and/ordata.

In various embodiments, secondary memory may include other similardevices for allowing computer programs or other instructions to beloaded into a computer system. Such devices may include, for example, aremovable storage unit and an interface. Examples of such may include aprogram cartridge and cartridge interface (such as that found in videogame devices), a removable memory chip (such as an erasable programmableread only memory (EPROM), programmable read only memory (PROM)) andassociated socket, or other removable storage units and interfaces,which allow software and data to be transferred from the removablestorage unit to a computer system.

The computer system may also include a communications interface. Acommunications interface allows software and data to be transferredbetween the computer system and external devices. Examples ofcommunications interface may include a modem, a network interface (suchas an Ethernet card), a communications port. etc. Software and datatransferred via the communications interface are in the form of signalswhich may be electronic, electromagnetic, optical, or other signalscapable of being received by communications interface. These signals areprovided to communications interface via a communications path (e.g.,channel). This channel carries signals and may be implemented usingwire, cable, fiber optics, a telephone line, a cellular link, a radiofrequency (RF) link, wireless and other communications channels.

In various embodiments, the server may include application servers(e.g., WEBSPHERE®, WEBLOGIC®, JBOSS®, POSTGRES PLUS ADVANCED SERVER®,etc.). In various embodiments, the server may include web servers (e.g.,Apache, IIS, GOOGLE® Web Server, SUN JAVA® System Web Server, JAVA®Virtual Machine running on LINUX® or WINDOWS® operating systems).

A web client includes any device or software which communicates via anynetwork, such as, for example any device or software discussed herein.The web client may include internet browsing software installed within acomputing unit or system to conduct online transactions and/orcommunications. These computing units or systems may take the form of acomputer or set of computers, although other types of computing units orsystems may be used, including personal computers, laptops, notebooks,tablets, smart phones, cellular phones, personal digital assistants,servers, pooled servers, mainframe computers, distributed computingclusters, kiosks, terminals, point of sale (POS) devices or terminals,televisions, or any other device capable of receiving data over anetwork. The web client may include an operating system (e.g., WINDOWS®,WINDOWS MOBILE® operating systems, UNIX® operating system, LINUX®operating systems, APPLE® OS® operating systems, etc.) as well asvarious conventional support software and drivers typically associatedwith computers. The web-client may also run MICROSOFT® INTERNETEXPLORER® software, MOZILLA® FIREFOX® software, GOOGLE® CHROME®software, APPLE® SAFARI' software, or any other of the myriad softwarepackages available for browsing the internet.

As those skilled in the art will appreciate, the web client may or maynot be in direct contact with the server (e.g., application server, webserver, etc., as discussed herein). For example, the web client mayaccess the services of the server through another server and/or hardwarecomponent, which may have a direct or indirect connection to an internetserver. For example, the web client may communicate with the server viaa load balancer. In various embodiments, web client access is through anetwork or the internet through a commercially-available web-browsersoftware package. In that regard, the web client may be in a home orbusiness environment with access to the network or the internet. The webclient may implement security protocols such as Secure Sockets Layer(SSL) and Transport Layer Security (TLS). A web client may implementseveral application layer protocols including HTTP, HTTPS, FTP, andSFTP.

Any of the communications, inputs, storage, databases or displaysdiscussed herein may be facilitated through a website having web pages.The term “web page” as it is used herein is not meant to limit the typeof documents and applications that might be used to interact with theuser. For example, a typical website might include, in addition tostandard HTML documents, various forms, JAVA® applets JAVASCRIPT®programs, active server pages (ASP), common gateway interface scripts(CGI), extensible markup language (XML), dynamic HTML, cascading stylesheets (CSS), AJAX (Asynchronous JAVASCRIPT And XML) programs, helperapplications, plug-ins and the like. A server may include a web servicethat receives a request from a web server, the request including a URLand an IP address (192.168.1.1). The web server retrieves theappropriate web pages and sends the data or applications for the webpages to the IP address. Web services are applications that are capableof interacting with other applications over a communications means, suchas the internet. Web services are typically based on standards orprotocols such as XML, SOAP, AJAX, WSDL and UDDI. Web services methodsare well known in the art, and are covered in many standard texts. Forexample, representational state transfer (REST), or RESTful, webservices may provide one way of enabling interoperability betweenapplications.

The computing unit of the web client may be further equipped with aninternet browser connected to the internet or an intranet using standarddial-up, cable, DSL, or any other internet protocol known in the art.Transactions originating at a web client may pass through a firewall inorder to prevent unauthorized access from users of other networks.Further, additional firewalls may be deployed between the varyingcomponents of CMS to further enhance security.

Encryption may be performed by way of any of the techniques nowavailable in the art or which may become available—e.g., Twofish, RSA,El Gamal, Schorr signature, DSA, PGP, PM, GPG (GnuPG), HPEFormat-Preserving Encryption (FPE), Voltage, Triple DES, Blowfish, AES,MD5, HMAC, IDEA, RC6, and symmetric and asymmetric cryptosystems. Thesystems and methods may also incorporate SHA series cryptographicmethods, elliptic curve cryptography (e.g., ECC, ECDH, ECDSA, etc.),and/or other post-quantum cryptography algorithms under development.

Any databases discussed herein may include relational, hierarchical,graphical, blockchain, object-oriented structure, and/or any otherdatabase configurations. Any database may also include a flat thestructure wherein data may be stored in a single file in the form ofrows and columns, with no structure for indexing and no structuralrelationships between records. For example, a flat file structure mayinclude a delimited text file, a CSV (comma-separated values) file,and/or any other suitable flat file structure. Common database productsthat may be used to implement the databases include DB2® by IBM®(Armonk, N.Y.), various database products available from ORACLE®Corporation (Redwood Shores, Calif.), MICROSOFT ACCESS® or MICROSOFT SQLSERVER® by MICROSOFT® Corporation (Redmond, Wash.), MYSQL® by MySQL AB(Uppsala, Sweden), MONGODB®, Redis, APACHE CASSANDRA®, HBASE® byAPACHE®, MapR-DB by the MAPR® corporation, or any other suitabledatabase product. Moreover, any database may be organized in anysuitable manner, for example, as data tables or lookup tables. Eachrecord may be a single file, a series of files, a linked series of datafields, or any other data structure.

Association of certain data may be accomplished through any desired dataassociation technique such as those known or practiced in the art. Forexample, the association may be accomplished either manually orautomatically. Automatic association techniques may include, forexample, a database search, a database merge, GREP, AGREP, SQL, using akey field in the tables to speed searches, sequential searches throughall the tables and files, sorting records in the file according to aknown order to simplify lookup, and/or the like. The association stepmay be accomplished by a database merge function, for example, using a“key field” in pre-selected databases or data sectors. Various databasetuning steps are contemplated to optimize database performance. Forexample, frequently used files such as indexes may be placed on separatefile systems to reduce In/Out (“I/O”) bottlenecks.

More particularly, a “key field” partitions the database according tothe high-level class of objects defined by the key field. For example,certain types of data may be designated as a key field in a plurality ofrelated data tables and the data tables may then be linked on the basisof the type of data in the key field. The data corresponding to the keyfield in each of the linked data tables is preferably the same or of thesame type. However, data tables having similar, though not identical,data in the key fields may also be linked by using AGREP, for example.In accordance with one embodiment, any suitable data storage techniquemay be utilized to store data without a standard format. Data sets maybe stored using any suitable technique, including, for example, storingindividual files using an ISO/IEC 7816-4 file structure; implementing adomain whereby a dedicated file is selected that exposes one or moreelementary files containing one or more data sets; using data setsstored in individual files using a hierarchical filing system; data setsstored as records in a single file (including compression, SQLaccessible, hashed via one or more keys, numeric, alphabetical by firsttuple, etc.); data stored as Binary Large Object (BLOB); data stored asungrouped data elements encoded using ISO/IEC 7816-6 data elements; datastored as ungrouped data elements encoded using ISO/IEC Abstract SyntaxNotation (ASN.1) as in ISO/IEC 8824 and 8825; other proprietarytechniques that may include fractal compression methods, imagecompression methods, etc.

In various embodiments, the ability to store a wide variety ofinformation in different formats is facilitated by storing theinformation as a BLOB. Thus, any binary information can be stored in astorage space associated with a data set. As discussed above, the binaryinformation may be stored in association with the system or external tobut affiliated with system. The BLOB method may store data sets asungrouped data elements formatted as a block of binary via a fixedmemory offset using either fixed storage allocation, circular queuetechniques, or best practices with respect to memory management (e,g.,paged memory, least recently used, etc.). By using BLOB methods, theability to store various data sets that have different formatsfacilitates the storage of data, in the database or associated with thesystem, by multiple and unrelated owners of the data sets. For example,a first data set which may be stored may be provided by a first party, asecond data set which may be stored may be provided by an unrelatedsecond party, and yet a third data set which may be stored, may beprovided by an third party unrelated to the first and second party. Eachof these three exemplary data sets may contain different informationthat is stored using different data storage formats and/or techniques.Further, each data set may contain subsets of data that also may bedistinct from other subsets.

As stated above, in various embodiments, the data can be stored withoutregard to a common format. However, the data set (e.g., BLOB) may beannotated in a standard manner when provided for manipulating the datain the database or system. The annotation may comprise a short header,trader, or other appropriate indicator related to each data set that isconfigured to convey information useful in managing the various datasets. For example, the annotation may be called a “condition header,”“header,” “trailer,” or “status,” herein, and may comprise an indicationof the status of the data set or may include an identifier correlated toa specific issuer or owner of the data. In one example, the first threebytes of each data set BLOB may be configured or configurable toindicate the status of that particular data set; e.g., LOADED,INITIALIZED, READY, BLOCKED, REMOVABLE, or DELETED. Subsequent bytes ofdata may be used to indicate for example, the identity of the issuer,user, transaction/membership account identifier or the like. Each ofthese condition annotations are further discussed herein.

The data set annotation may also be used for other types of statusinformation as well as various other purposes. For example, the data setannotation may include security information establishing access levels.The access levels may, for example, be configured to permit only certainindividuals, levels of employees, companies, or other entities to accessdata sets, or to permit access to specific data sets based on thetransaction, merchant, issuer, user, or the like. Furthermore, thesecurity information may restrict/permit only certain actions such asaccessing, modifying, and/or deleting data sets. In one example, thedata set annotation indicates that only the data set owner or the userare permitted to delete a data set, various identified users may bepermitted to access the data set for reading, and others are altogetherexcluded from accessing the data set. However, other access restrictionparameters may also be used allowing various entities to access a dataset with various permission levels as appropriate.

The data, including the header or trailer, may be received by astandalone interaction device configured to add, delete, modify, oraugment the data in accordance with the header or trailer. As such, inone embodiment, the header or trailer is not stored on the transactiondevice along with the associated issuer-owned data but instead theappropriate action may be taken by providing to the user at thestandalone device, the appropriate option for the action to be taken.The system may contemplate a data storage arrangement wherein the headeror trailer, or header or trailer history, of the data is stored on thesystem, device or transaction instrument in relation to the appropriatedata.

One skilled in the art will also appreciate that, for security reasons,any databases, systems, devices, servers, or other components of thesystem may consist of any combination thereof at a single location or atmultiple locations, wherein each database or system includes any ofvarious suitable security features, such as firewalls, access codes,encryption, decryption, compression, decompression, and/or the like.

Practitioners will also appreciate that there are a number of methodsfor displaying data within a browser-based document. Data may berepresented as standard text or within a fixed list, scrollable list,drop-down list, editable text field, fixed text field, pop-up window,and the like. Likewise, there are a number of methods available formodifying data in a web page such as, for example, free text entry usinga keyboard, selection of menu items, check boxes, option boxes, and thelike.

Distributed computing cluster may be, for example, a HADOOP® softwarecluster configured to process and store big data sets with some of nodescomprising a distributed storage system and some of nodes comprising adistributed processing system. In that regard, distributed computingcluster may be configured to support a HADOOP® software distributed filesystem (HDFS) as specified by the Apache Software Foundation atwww.hadoop.apache.org/docs.

As used herein, the term “network” includes any cloud, cloud computingsystem, or electronic communications system or method which incorporateshardware and/or software components. Communication among the parties maybe accomplished through any suitable communication channels, such as,for example, a telephone network, an extranet, an intranet, internet,point of interaction device (point of sale device, personal digitalassistant (e.g., an IPHONE® device, a BLACKBERRY® device), cellularphone, kiosk, etc.), online communications, satellite communications,off-line communications, wireless communications, transpondercommunications, local area network (LAN), wide area network (WAN),virtual private network (VPN), networked or linked devices, keyboard,mouse, and/or any suitable communication or data input modality.Moreover, although the system is frequently described herein as beingimplemented with TCP/IP communications protocols, the system may also beimplemented using IPX, APPLETALK® program, IP-6, NetBIOS, OSI, anytunneling protocol (e.g. IPsec, SSH, etc.), or any number of existing orfuture protocols. If the network is in the nature of a public network,such as the internet, it may be advantageous to presume the network tobe insecure, and open to eavesdroppers. Specific information related tothe protocols, standards, and application software utilized inconnection with the internet is generally known to those skilled in theart and, as such, need not be detailed herein.

“Cloud” or “Cloud computing” includes a model for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, servers, storage, applications, and services)that can be rapidly provisioned and released with minimal managementeffort or service provider interaction. Cloud computing may include,location-independent computing, whereby shared servers provideresources, software, and data to computers and other devices on demand.

As used herein “transmit” may include sending electronic data from onesystem component to another over a network connection. Additionally, asused herein, “data” may include encompassing information such ascommands, queries, files, data for storage, and the like in digital orany other form.

Therefore, the following is claimed:
 1. A system, comprising: a computing device comprising a processor and a memory; and machine-readable instructions stored in the memory that, when executed by the processor, cause the computing device to at least: receive a migration request for migrating data associated with a source file from a first data environment to a second data environment; convert the source file into a compressed format; identify personally identifiable information from the source file in the compressed format; and in response to receiving an approval to migrate the data from the first data environment to the second data environment from a user associated with the personally identifiable information, transfer the source file in the compressed format from the first data environment to the second data environment.
 2. The system of claim 1, wherein the first data environment is associated with a private network and the second data environment is associated with a public network.
 3. The system of claim 1, wherein converting the source file into the compressed format comprises using a parquet conversion function to convert the source file into a parquet file.
 4. The system of claim 1, wherein, when executed, the machine-readable instructions causes the computing device to at least capture source file metadata associated with the source file based at least in part on a source file path included in the migration request.
 5. The system of claim 4, wherein the source file metadata comprises at least one of a number of columns transferred, user information, one or more timestamps associated with a start or an end of a transfer, or a predicted transfer time.
 6. The system of claim 1, wherein, when executed, the machine-readable instructions further cause the computing device to at least: generate a message in response to identifying the personally identifiable information, the message comprising an approval link for approving a migration of the data; and transmit the message to a client device associated with the user.
 7. The system of claim 1, wherein transferring the source file in the compressed format from the first data environment to the second data environment comprises: transferring the source file from the first data environment to an intermediate data environment via a first transfer process; and transferring the source file from the intermediate data environment to the second data environment via a second transfer process.
 8. A method comprising: receiving, by at least one computing device, a migration request for migrating data associated with a source file from a first data environment to a second data environment; identifying, by the at least one computing device, personally identifiable information from the source file; and in response to receiving an approval to migrate the data from the first data environment to the second data environment from a user associated with the personally identifiable information, transferring the source file from the first data environment to the second data environment.
 9. The method of claim 8, further comprising converting the source file into a compressed format prior to transferring the source file from the first data environment to the second data environment.
 10. The method of claim 8, further comprising: generating, by the at least one computing device, a message in response to identifying the personally identifiable information, the message comprising an approval link for approving a migration of the data; and sending, by the at least one computing device, the message to a client device associated with the user.
 11. The method of claim 8, further comprising: generating a user interface comprising a migration status associated with a migration of the data; and updating the user interface in response to one or more changes in the migration status.
 12. The method of claim 8, further comprising capturing source file metadata associated with the source file, the source file metadata comprising at least one of a number of columns transferred, user information, one or more timestamps associated with a start or an end of a transfer, or a predicted transfer time.
 13. The method of claim 8, wherein the data is migrated from the first data environment to an intermediary data environment prior to being transferred to the second data environment.
 14. The method of claim 8, further comprising: causing a transfer process to be placed in a hold state in response to identifying the personally identifiable information; and causing the transfer process to exit the hold state and resume with the transfer process in response to receiving the approval to migrate the data from the user.
 15. A non-transitory computer readable medium comprising machine-readable instructions that, when executed, by a processor of a computing device, cause the computing device to at least: convert a source file into a compressed format; identify personally identifiable information from the source file in the compressed format; and in response to receiving an approval from a user associated with the personally identifiable information, transfer the source file in the compressed format from a first data environment to a second data environment.
 16. The non-transitory computer readable medium of claim 15, wherein, when executed, the machine-readable instructions further cause the computing device to at least receive a migration request for migrating data associated with the source file from the first data environment to the second data environment, the migration request comprising a source file location and a target file location.
 17. The non-transitory computer readable medium of claim 15, wherein the first data environment is associated with a private network and the second data environment is associated with a public network.
 18. The non-transitory computer readable medium of claim 15, wherein, when executed, the machine-readable instructions further cause the computing device to at least: generate a message in response to identifying the personally identifiable information, the message comprising an approval link for approving a migration of data included in the source file; and send the message to a client device associated with the user.
 19. The non-transitory computer readable medium of claim 15, wherein, when executed, the machine-readable instructions further cause the computing device to at least: generate a user interface comprising a migration status associated with transferring the source file from the first data environment to the second data environment; and cause the user interface to be rendered on a client device.
 20. The non-transitory computer readable medium of claim 19, wherein the migration status is based at least in part on source file metadata associated with the source file, the source file metadata comprising at least one of a number of columns transferred, user information, one or more timestamps associated with a start or an end of a transfer, or a predicted transfer time. 